@fen84

has anyone been able to get Mario Kart Arcade GP (or 2) MAME working?

'Mario Kart Arcade GP' runs on the Triforce arcade system which is based on GameCube hardware. Unfortunately the Raspberry Pi isn't nearly powerful enough to emulate a system that demanding.

As for the rest of your issues, You can't just "pop" any old ROM in the arcade folder. You need to get a specific numbered ROM set for the arcade emulator you've chosen. For example, the default arcade emulator in RetroPie is lr-mame2003, which uses the MAME 0.78 ROM set. Anything outside of the intended ROM set for your chosen emulator will usually result in failure. Also, as a rule of thumb, any game north of 1995 has an increasingly higher chance of running poorly on the Pi.

Everything you need to know for arcade emulation in RetroPie is covered here.

@deveee should I unistall the version I already have before compiling it with STK 0.9.3?

@arturgomes I love how janky it is

@rak7145 said in RetroPie won't boot on Raspberry Pi 3:

I encountered an error numerous times that said Etcher couldn't locate the disk

I haven't had this happen myself though it's possible there's something up with your SD card/ SD card reader. There are lots of shady eBay SD sellers, I try and stick with reputable sources, if you have another microsd laying around might be worth trying and if for some reason it's etcher you can try win32diskimager instead to rule that out as well though I personally have never had issues with etcher.

If above fails also try diff HDMI if possible but I wouldn't necessarily go buying all sorts of new hardware until I've tried every software fix.

@isrnick I second this method. I don't know what started causing it but after a certain point every card I re-write I have to delete partitions/volumes.

try this inside the minecraft.sh write

#!/bin/bash
xset -dpms s off s noblank
matchbox-window-manager &
/usr/bin/minecraft-pi

You can try to use the SD Card Copier that is now available in Raspbian. I don't know if it's available in Jessie tho, so I'm not sure if you could install Raspbian within Retropie and copy your running SD to an SD connected via USB.
Otherwise you need to set up an extra Card just with Raspbian and use two card readers to clone your card. The tool will clone your card to smaller/bigger cards and shrink/expand the filesystem automatically.
I only tried it with my OSMC card and got an error message on the new card, but OSMC is not suppose to have the filesystem size changed afterwards and i was using an older Noobs version. So I'm not sure if it would work with Retropie flawlessly and i don't have spare cards to test it.

If you are used to an OS such as Winodws or Mac, then Linux is a pretty steep learning curve. It took me a few days of reading and getting it wrong and reinstalling Raspbian more than once to work out what was happening. I installed RetroPie from the manual install script a couple of times as well. You won't damage your PI but maybe get frustrated and banging your head against the table trying to work out what won't work and why

There is quite a bit of manual installation even after getting RetroPie up and running. Linux is a good OS but needs a fair bit of user assistance to get it running how YOU want it to run, especially in allowing access to various parts that you normally wouldn't be able to access to give you more control over it

Once it is running, RetroPie is a breeze to use and very simple to add to as and when YOU want to including adding or removing ROMs or emulator systems, unlike Windows that constantly badgers you for yet another security/software update (especially Windows 10 that has taken ALL the control away from the user when updates are needs .... or that Microsoft believe is needed)

Did you read this guide, it helps a LOT

https://github.com/retropie/retropie-setup/wiki/First-Installation

@mitu Coincidentally, I tried stretch with his mame build last week and it ran like dogcrap. I tried a neogeo game and ran at 30% speed.

@darksavior Well, It's an all new retropie emulation now, I tried (waiting to received a good power supply) with my Google home mini power supply, and all roms now work flawlessly !!
Thanks again for your advises !

@fabz384lakers Filled the memory? You mean filled the storage (of the SD card). They are different things...

Yes provide an error message, if any, like mitu has asked..that will help us help you faster...

However I am going to assume that your card was filled to the last bit..and thus caused corruption of the card. Works the same way with a spinning hard drive..

Let's figure out IF that is the case first..and if it is then we can try to recover your card...

Here are some tests i have done :

$ jstest /dev/input/js0 Driver version is 2.1.0. Joystick (PowerA Xbox One wired controller) has 6 axes (X, Y, Rx, Ry, Hat0X, Hat0Y) and 13 buttons (BtnX, BtnY, BtnTL, BtnTR, BtnTR2, BtnSelect, BtnStart, BtnMode, BtnThumbL, BtnThumbR, ?, ?, ?). Testing ... (interrupt to exit) Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off 12:off $ lsmod | grep xpad xpad 18566 0 ff_memless 5315 1 xpad $ evtest /dev/input/event[0] Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x24c6 product 0x543a version 0x101 Input device name: "PowerA Xbox One wired controller" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 304 (BTN_SOUTH) Event code 305 (BTN_EAST) Event code 307 (BTN_NORTH) Event code 308 (BTN_WEST) Event code 310 (BTN_TL) Event code 311 (BTN_TR) Event code 312 (BTN_TL2) Event code 313 (BTN_TR2) Event code 314 (BTN_SELECT) Event code 315 (BTN_START) Event code 316 (BTN_MODE) Event code 317 (BTN_THUMBL) Event code 318 (BTN_THUMBR) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 1 (ABS_Y) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 3 (ABS_RX) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 4 (ABS_RY) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 16 (ABS_HAT0X) Value 0 Min -1 Max 1 Event code 17 (ABS_HAT0Y) Value 0 Min -1 Max 1 Event type 21 (EV_FF) Event code 80 (FF_RUMBLE) Event code 81 (FF_PERIODIC) Event code 88 (FF_SQUARE) Event code 89 (FF_TRIANGLE) Event code 90 (FF_SINE) Event code 96 (FF_GAIN)

@nextria I'd say dodgy LAN port or cable then.

@mitu Thanks for the quick response. I just ended up using my Pi1 and used a 2.5 speaker jack. Odd reason that pi3 did not want to pick up the 2.5 speaker jack or find the USB speaker... Weird.

@jblock22 On the bright side, you do have what sounds like a Pi3, which is a supported computer, you have a cabinet someone built with arcade controls, USB ports, a display, and a nice enough design that you were interested in buying it. A build project with just this hardware alone is a serious undertaking, and getting one that looks nice enough to sell is no small feat. Depending on how it was built, you might also have a controls interface of some kind.

Now, the software is the real questionable part of all of this, but you can easily re image the SD card with a known working image from this website and join the community. You will need to open up your system and do some investigating into what exactly you have which might entail some google searching as well, but once you know what you have and you are willing to work with it, you can probably turn this in to a great system. It will take work and interest, but it can be a fun hobby.

Maybe that is not why you bought it, but there could be a silver lining.

ok I found a solution.
If I use 2 ps3 DUALSHOCK3 controller (exactly the same model) everything works well.

:)
Dani